Billing — the invoicing bounded context
The money ledger: one billing profile per organization — currency and method — and the invoice lifecycle from issued through due, overdue and paid. THB for the reference organizations; the currency always comes from the profile, never assumed. A generic subdomain — a commodity capability, a candidate to buy.
1Ownership & boundaries
Billing owns the profile and the invoice — nothing about pricing (Tenancy's plans) or deal value (Sales). Won-deal drafts arrive by event; RiverSync accounting issues and reconciles. Partner visibility into agreement-related invoices is a scope switch on the Coverage grant, resolved like every other partner read.
Reads from: Tenancy (organization, currency at bootstrap) · Sales (won deals to invoice). Account is the customer surface; Admin the RiverSync one.
2Ubiquitous language
The words this context uses — the same in code, conversation and spec.
3Aggregates & invariants
The consistency boundaries — one root each, guarding its invariants in a single transaction; cross-aggregate ties are by identity.
4Context relationships
How this context meets its neighbours — downstream customer/supplier of Sales (won deals to invoice) and Federation (profile bootstrap).
5Physical view — the service API
The deployment mapping: this context becomes the Billing service. Paths relative to api.riversync.com/v1; access notation per the master.